Managing The Display Of Applications For Financial Institutions

ABSTRACT

A method and system according to which applications are displayed on a display system via a management platform. User input is received, which identifies a selected application from the plurality of applications. A current status of an application process is determined. The current status of the application corresponds to the selected application using application data associated with the selected application that is stored in an application database. An application timeline and a subphase progression are displayed via the management platform on the display system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of the filing date of, and priorityto U.S. Patent Application No. 63/305,578, filed on Feb. 1, 2022, theentire disclosure of which is hereby incorporated herein by reference.

This application is related to U.S. application Ser. No. ______,Attorney Docket No. 60727.5US02, filed even date hereof, entitled“Building an Online Application Platform for a Client FinancialInstitution,” the entire disclosure of which is hereby incorporatedherein by reference.

FIELD

The present disclosure relates generally to managing applications forfinancial institutions. More particularly, the present disclosurerelates to methods and systems for managing applications for membershipto financial institutions and/or applications for financial productsprovided by financial institutions and to methods and systems forcustomizing an online application platform through which suchapplications are processed (e.g., initiated and completed).

BACKGROUND

Different types of financial institutions offer different types offinancial products such as, for example, checking accounts, savingsaccounts, loans, trust accounts, etc. Examples of financial institutionsinclude traditional banks and credit unions. A “credit union” is amember-owned financial cooperative that is non-profit and provides itsmembers with financial rates (e.g., loans, certificates of deposit,etc.), financial products (e.g., checking shares and loans), and otherservices that are competitive and exclusive to its members. While a bankmay offer many of the same financial products as a credit union, a bankdiffers from a credit union in that a bank is typically a for-profitinstitution that is not member-owned.

Currently, financial institutions may employ electronic, software-basedplatforms to accept and manage applications for membership to and/orapplications for the financial products provided by these financialinstitutions. These known, software-based platforms offer limitedfunctionality and are difficult to design, build, andmaintain—especially for smaller, community-based banking institutionssuch as credit unions. For example, at any given point in time, afinancial institution may need to monitor or track tens to hundreds orthousands of applications simultaneously, with many of theseapplications being at different stages in the application process.Monitoring these applications over time may be difficult,time-consuming, and overly cumbersome using existing software platforms.Further, with both commercially-available software platforms andcustom-built software platforms, a financial institution may find itinefficient or difficult to initially customize or make desiredmodifications to an already-deployed applicant-facing user interface.

Therefore, it may be desirable to have methods and/or systems thataddress one or more of the issues described above, as well as otherpossible issues.

SUMMARY

In one or more embodiments, a method is provided for monitoring a set ofapplications for a set of financial products provided by a financialinstitution. The set of applications is displayed via a managementplatform on a display system. Each application of the set ofapplications is associated with application data stored in anapplication database. User input identifying a selected application fromthe set of applications is received. A current status of an applicationprocess corresponding to the selected application is determined usingthe application data associated with the selected application. Anapplication timeline comprising a plurality of phases in the applicationprocess is displayed via the management platform on the display system.The application timeline indicates a current phase of the plurality ofphases in the application process based on the current status. Asubphase progression comprising a plurality of subphases within thecurrent phase is displayed via the management platform on the displaysystem. The subphase progression indicates a current subphase of theplurality of subphases based on the current status.

In one or more embodiments, a system is provided for monitoring a set ofapplications for a set of financial products provided by a financialinstitution. The system comprises a memory containing a machine-readablemedium containing instructions; and a processor coupled to the memory.The processor is configured to execute the instructions to cause theprocessor to: display the set of applications via a management platformon a display system, wherein each application of the set of applicationsis associated with application data stored in an application database;receive user input identifying a selected application from the set ofapplications; determine a current status of an application processcorresponding to the selected application using the application dataassociated with the selected application; display, via the managementplatform, an application timeline comprising a plurality of phases inthe application process, wherein the application timeline indicates acurrent phase of the plurality of phases in the application processbased on the current status; and display, via the management platform, asubphase progression comprising a plurality of subphases within thecurrent phase, wherein the subphase progression indicates a currentsubphase of the plurality of subphases based on the current status.

In one or more embodiments, a method is provided for monitoring anapplication of a user for a set of financial products provided by acredit union. An input selecting the application is received via amanagement platform displayed on a display system. The application isassociated with application data stored in an application database. Acurrent status of an application process corresponding to theapplication is determined using the application data associated with theselected application. An application timeline comprising a plurality ofphases in the application process is displayed via the managementplatform. The plurality of phases includes a workflow phase and at leastone of a qualify phase, a decision phase, or a processing phase. Theapplication timeline indicates, based on the current status, that theworkflow phase is a current phase in the application process using afirst in-progress indicator. A subphase progression comprising aplurality of subphases within the workflow phase is displayed via themanagement platform on the display system. The subphase progressionindicates, based on the current status, a current subphase of theplurality of subphases using a second in-progress indicator.

In one or more embodiments, a method is provided for building an onlineapplication platform for a client financial institution. A defaultconfiguration for the online application platform is provided. Thedefault configuration comprises a default application framework and adefault theme. The default application framework defines a default setof account types and a default set of financial products for anapplication. The default theme defines an appearance of the onlineapplication platform. A management interface accessible by the clientfinancial institution is provided. The management interface includes aframework tool for customizing the default application framework and atheme tool for customizing the default theme. A first set of inputs thatselects a set of financial products from a list of predefined financialproducts is received by the framework tool. The set of financialproducts is to be offered by the client financial institution via theonline application platform. The default application framework isconverted by the framework tool into a customized application framework,the converting comprising modifying the online application platform tooffer the set of financial products selected via the first set ofinputs. A second set of inputs is received by the theme tool, each inputof the second set of inputs selecting a value for a respectivecharacteristic of the appearance of the online application platform, thevalue corresponding with a branding of the client financial institution.The default theme is converted by the theme tool into a customizedtheme, the converting comprising modifying the appearance of the onlineapplication platform to reflect the value for the respectivecharacteristic. The customized configuration of the online applicationplatform is provided, via a network, to one or more applicants of theclient financial institution. The customized configuration comprises thecustomized application framework and the customized theme.

In one or more embodiments, a system is provided for building an onlineapplication platform for a client financial institution. The systemcomprises a memory containing a machine-readable medium containinginstructions; and a processor coupled to the memory. The processor isconfigured to execute the instructions to cause the processor to providea default configuration for an online application platform. The defaultconfiguration comprises a default application framework and a defaulttheme. The default application framework defines a default set ofaccount types and a default set of financial products for anapplication. The default theme defines an appearance of the onlineapplication platform. The processor is configured to execute theinstructions to cause the processor to provide a management interfaceaccessible by the client financial institution. The management interfaceincludes a framework tool for customizing the default applicationframework and a theme tool for customizing the default theme. Theprocessor is configured to execute the instructions to cause theprocessor to receive, by the framework tool, a first set of inputs thatselects a set of financial products from a list of predefined financialproducts. The set of financial products is to be offered by the clientfinancial institution via the online application platform. The processoris configured to execute the instructions to cause the processor toconvert, by the framework tool, the default application framework into acustomized application framework, the converting comprising modifyingthe online application platform to offer the set of financial productsselected via the first set of inputs. The processor is configured toexecute the instructions to cause the processor to receive, by the themetool, a second set of inputs, each input of the second set of inputsselecting a value for a respective characteristic of the appearance ofthe online application platform, the value corresponding with a brandingof the client financial institution. The processor is configured toexecute the instructions to cause the processor to convert, by the themetool, the default theme into a customized theme, the convertingcomprising modifying the appearance of the online application platformto reflect the value for the respective characteristic selected by eachinput of the second set of inputs. The processor is configured toexecute the instructions to cause the processor to provide, via anetwork, a customized configuration of the online application platformto applicants of the client financial institution, the customizedconfiguration comprising the customized application framework and thecustomized theme.

In one or more embodiments, a method is provided for customizing anapplication platform for a client financial institution. A defaultconfiguration for the online application platform is provided, thedefault configuration comprising a default application framework and adefault theme. The default application framework defines a default setof account types and a default set of financial products for anapplication. A management interface accessible by the client financialinstitution is provided, the management interface including a frameworktool for customizing the default application framework. A first set ofinputs that selects a set of account types from a list of predefinedaccount types is received by the framework tool. Each of the set ofaccount types corresponds to a different type of membership for theclient financial institution. A second set of inputs that selects a setof financial products from a list of predefined financial products isreceived by the framework tool. The set of financial products is to beoffered by the client financial institution via the online applicationplatform. A third set of inputs that selects a set of third-partyservices from a list of predefined third-party services is received bythe framework tool. The default application framework is converted, bythe framework tool, into a customized application framework, theconverting comprising modifying the online application platform based onthe first set of inputs, the second set of inputs, and the third set ofinputs.

The features and functions can be achieved independently in variousembodiments of the present disclosure or may be combined in yet otherembodiments in which further details can be seen with reference to thefollowing description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the illustrativeembodiments are set forth in the appended claims. The illustrativeembodiments, however, as well as a preferred mode of use, furtherobjectives and features thereof, will best be understood by reference tothe following detailed description of an illustrative embodiment of thepresent disclosure when read in conjunction with the accompanyingdrawings, wherein:

FIG. 1 is an illustration of an application system 100 in accordancewith one or more embodiments.

FIG. 2 is an illustration of a backend user interface in accordance withone or more embodiments.

FIG. 3 is another illustration of the backend user interface from FIG. 2in accordance with one or more embodiments.

FIG. 4 is another illustration of the backend user interface from FIGS.2-3 in accordance with one or more embodiments.

FIG. 5 is another illustration of the backend user interface from FIGS.2-4 in accordance with one or more embodiments.

FIG. 6 is an illustration of an enlarged view of tracking informationand a current status section of an application section within thebackend user interface from FIG. 3 in accordance with one or moreembodiments.

FIG. 7 is another illustration of an enlarged view of trackinginformation and a current status section of an application sectionwithin the backend user interface from FIG. 3 in accordance with one ormore embodiments.

FIG. 8 is another illustration of an enlarged view of trackinginformation and a current status section of an application sectionwithin the backend user interface from FIG. 3 in accordance with one ormore embodiments.

FIG. 9 is another illustration of an enlarged view of trackinginformation and a current status section of an application sectionwithin the backend user interface from FIG. 3 in accordance with one ormore embodiments.

FIG. 10 is an illustration of the backend user interface from FIGS. 3-5in accordance with one or more embodiments.

FIG. 11 is an illustration of the backend user interface from FIG. 2 inaccordance with one or more embodiments.

FIG. 12 is another illustration of the backend user interface from FIG.11 in accordance with one or more embodiments.

FIG. 13 is another illustration of the backend user interface from FIGS.11-12 in accordance with one or more embodiments.

FIG. 14 is another illustration of the backend user interface from FIGS.11-13 in accordance with one or more embodiments.

FIG. 15 is another illustration of the backend user interface from FIGS.11-14 in accordance with one or more embodiments.

FIG. 16 is another illustration of the backend user interface from FIG.15 in accordance with one or more embodiments.

FIG. 17 is an illustration of the backend user interface from FIG. 2 inaccordance with one or more embodiments.

FIG. 18 is another illustration of the backend user interface from FIG.17 in accordance with one or more embodiments.

FIG. 19 is another illustration of the backend user interface from FIGS.17-18 in accordance with one or more embodiments.

FIG. 20 is another illustration of the backend user interface from FIGS.17-19 in accordance with one or more embodiments.

FIG. 21 is another illustration of the backend user interface from FIGS.17-20 in accordance with one or more embodiments.

FIG. 22 is another illustration of the backend user interface from FIG.17 in accordance with one or more embodiments.

FIG. 23 is an illustration of a frontend user interface in accordancewith one or more embodiments.

FIG. 24 is another illustration of the backend user interface from FIG.22 in accordance with one or more embodiments.

FIG. 25 is another illustration of the frontend user interface from FIG.23 in accordance with one or more embodiments.

FIG. 26 is another illustration of the backend user interface from FIG.22 in accordance with one or more embodiments.

FIG. 27 is another illustration of the frontend user interface from FIG.23 in accordance with one or more embodiments.

FIG. 28 is another illustration of the backend user interface from FIG.22 in accordance with one or more embodiments.

FIG. 29 is another illustration of the frontend user interface from FIG.23 in accordance with one or more embodiments.

FIG. 30 is another illustration of the backend user interface from FIG.22 in accordance with one or more embodiments.

FIG. 31 is a flowchart of a process for monitoring a set of applicationsfor a set of financial products provided by a financial institution inaccordance with one or more embodiments.

FIG. 32 is a flowchart of a process for monitoring an application of auser for a set of financial products provided by a credit union inaccordance with one or more embodiments.

FIG. 33 is a flowchart of a process for building an online applicationplatform for a client financial institution in accordance with one ormore embodiments.

FIG. 34 is a flowchart of a process for customizing an applicationplatform for a client financial institution in accordance with one ormore embodiments.

FIG. 35 is an illustration of a data processing system in the form of ablock diagram is depicted in accordance with an illustrative embodiment.

DETAILED DESCRIPTION

Managing (e.g., monitoring, facilitating, etc.) the applications ofapplicants for membership to and/or for the financial products offeredby financial institutions (e.g., credit unions, banks) may be moredifficult, time-consuming, and cumbersome than desired for financialinstitutions. Currently existing computing systems and user interfacesmay be unable to simply and efficiently provide a snapshot of theprogress and current status of any selected application of the multipleapplications being managed by a financial institution. For example, somecurrently existing platforms may be unable to indicate both whether anapplication is in progress, and if so, where the application is at inthe overall process.

In some cases, an applicant seeking membership in a financialinstitution (e.g., a credit union) may initiate an application but notcomplete the application. Currently existing platforms may not providefinancial institutions with a way of tracking the progress of suchapplications and taking action (e.g., sending reminder emails,generating alerts, etc.) based on the progress of such applications.Currently existing platforms may be unable to, within a single visualarea, provide both a visual snapshot of the progress and current statusof an application, as well as information about the current status ofthe application and/or one or more controls for initiating actions basedon the current status.

Accordingly, the embodiments described herein provide methods andsystems for managing (e.g., monitoring, tracking, facilitating, etc.) aset of applications for a financial institution. In one or moreembodiments, a set of applications may be displayed via a managementplatform on a display system. For example, the set of applications maybe displayed via a backend user interface of the management platform.Each application of the set of applications may be associated withapplication data stored in an application database. User inputidentifying a selected application from the set of applications may bereceived via the backend user interface. A current status of anapplication process corresponding to the selected application may bedetermined using the application data associated with the selectedapplication. The backend user interface may display an applicationtimeline comprising a plurality of phases in the application process.The application timeline indicates a current phase of the plurality ofphases in the application process based on the current status. Further,the backend user interface may display a subphase progression comprisinga plurality of subphases within the current phase. The subphaseprogression indicates a current subphase of the plurality of subphasesbased on the current status.

In this manner, the backend user interface is able to provide amulti-layered snapshot of the progress and current status of theapplication process. This multi-layered approach (using both theapplication timeline and subphase progression) to track the status of anapplication may reduce the number of layers or data that the user wouldotherwise need to drill down through in order to discern the status ofthe application. By visually summarizing the most relevant information(e.g., current phase and current subphase) regarding the progress of anapplication in an application timeline and subphase progression, thebackend user interface allows the user to quickly discern the progressand current status of the application without the user needing toactually pull up the application itself, analyze the application datastored in the application database, and/or perform other time-consumingactions. For example, the user can quickly understand where anapplication stands without needing to open up the application processvia the online application platform and view the application itself viathe frontend user interface.

Further, currently existing platforms that host user interfaces forfinancial institutions may not provide these financial institutions witha way to quickly and easily self-customize the user interface that isprovided to an applicant. Currently, a user interface package may beprovided to a financial institution where the configuration for thatuser interface is generally static. After receiving the user interfacepackage, the financial institution may be unable to customize, forexample, the account types offered, the financial products offered, theintegration of third-party services, and/or the document types that canbe automatically or semi-automatically generated without having to goback to the entity that provided the user interface package.

Thus, the embodiments described herein provide methods and systems thatallow a financial institution to quickly and easily customize a defaultconfiguration for an online application platform and/or furthercustomize a previously customized configuration for the onlineapplication platform. With the methods and systems described herein, afinancial institution may independently perform such customizationwithout needing to reach out to the entity that provided the onlineapplication platform.

Referring now to the figures and, in particular, with reference to FIG.1 , an illustration of an application system 100 in accordance with oneor more embodiments. Application system 100 is one example of a systemthat can be used to manage (e.g., monitor, facilitate, etc.)applications to financial institution 102. Application system 100 may beprovided to financial institution 102 by entity 103 (e.g., financialinstitution 102 is a client of entity 103, where entity 103 may be asoftware developer or distributor). Accordingly, financial institution102 may also be referred to as a client financial institution. Financialinstitution 102 may take the form of a credit union (e.g., credit union104), a bank (e.g., bank 105), or some other type of financialinstitution. Bank 105 may be, for example, a local or regional bank, acommunity bank, or some other type of bank.

Application system 100 may be implemented using software, hardware,firmware, or any combination thereof. Application system 100 may beimplemented using, for example, without limitation, computing system106. Computing system 106 may include memory and one or more processors.In one or more embodiments, computing system 106 include a singlecomputer or multiple computers in communication with each other, one ormore servers, one or more storage devices, one or more display systems,one or more input devices, or any combination thereof. In one or moreembodiments, computing system 106 may include a cloud computing systemor platform. In one or more embodiments, computing system 106 includesmultiple computers, servers, or computing devices that are located in atleast two different locations. In one or more embodiments, computingsystem 106 is a server system and application system 100 may beimplemented as part of the server system. In one or more embodiments,computing system 106 provides application system 100 assoftware-as-a-service (SaaS) to entity 103.

Application system 100 includes application platform 108 and managementplatform 110. Each of application platform 108 may be implemented usingsoftware, hardware, firmware, or any combination thereof. Applicationplatform 108, management platform 110, or both may be in communicationwith database 111. Database 111 may include one or more databases and/orother types of data structures or data stores.

Application platform 108 includes frontend user interface 112, which isa graphical user interface that may be accessed using any type ofcomputing device (e.g., desktop, laptop, tablet, mobile phone, smartwatch, wearable device, etc.). In one or more embodiments, frontend userinterface 112 includes a web user interface (or web-based userinterface) that is accessed by members, customers, or applicants, and/orpotential members, potential customers, or applicants of financialinstitution 102 over a network (e.g., the Internet). Accordingly, in oneor more embodiments, application platform 108 may also be referred to asan online application platform.

In one or more embodiments, frontend user interface 112 takes the formof a n applicant-facing user interface intended for primary use by theapplicant of financial institution 102. In other embodiments, frontenduser interface 112 takes the form of an institution-facing userinterface intended for primary use by agents (e.g., employees) offinancial institution 102.

Frontend user interface 112 allows an applicant and/or agent offinancial institution 102 to initiate, progress through, and complete anapplication for financial institution 102. In one or more embodiments,this application is an application for membership to financialinstitution 102. For example, an applicant may use frontend userinterface 112 to apply for membership to financial institution 102 tothereby apply for a set of financial products provided by financialinstitution 102. The set of financial products may include at least oneof a checking account, a savings account, a money market account, acertificate of deposit (CD), a loan, a trust, or some other type offinancial product.

Data entered via frontend user interface 112 may be stored in database111. Accordingly, database 111 may also be referred to as an applicationdatabase or may include an application database for storing the data.The data associated with applications is referred to as application data113.

Management platform 110 may be used to manage (e.g., monitor,facilitate, etc.) applications entered via frontend user interface 112,customize a default version of online application platform 108 (e.g.,change an appearance of frontend user interface 112), further customizean already-customized version of online application platform 108, managethe security of and/or access to management platform 110 and/or onlineapplication platform 108, and/or manage application platform 108 inanother manner.

Management platform 110 includes backend user interface 114. Backenduser interface 114 is a graphical user interface that may be accessedusing any type of computing device (e.g., desktop, laptop, tablet,mobile phone, smart watch, wearable device, etc.). In one or moreembodiments, backend user interface 114 includes a web user interface(or web-based user interface) that is accessed by agents of financialinstitution 102 over a network (e.g., the Internet). Accordingly, in oneor more embodiments, management platform 110 may also be referred to asan online management platform.

Backend user interface 114, which may also be referred to as amanagement interface, is accessible by users who are agents of financialinstitution 102 or those authorized by financial institution 102.Backend user interface 114 includes process tracker 116, framework tool118, workflow experience tool 120, and theme tool 122. Process tracker116 may track, for example, application processes that are initiatedusing application platform 108. For example, process tracker 116 may becapable of tracking the progress and current status for the variousapplication processes of set of process types 124. Each process type maybe a different type of process that can be initiated and completed viafrontend user interface 112 of application platform 108. A process typemay be, for example, an application process, an account editing process,or some other type of process that can be stepped through using frontenduser interface 112. For example, set of process types 124 may includeset of application process types 125.

Set of application process types 125 may include, for example, at leastone of a membership application process, a trust application process, aloan application process, or another type of application process. Eachapplication process type of set of application process types 125 mayinclude one or more phases. These phases may include at least a workflowphase. The workflow phase (or workflow) may be the process or steps bywhich an application of a particular application type is initiated andcompleted by an applicant or an agent of financial institution 102assisting the applicant. For example, a workflow for a membershipapplication process may be similar to or different from the workflow fora trust application process, which may be similar to or different fromthe workflow for a loan application process.

An applicant using frontend user interface 112 can initiate and completean application for membership to financial institution 102 via aworkflow corresponding a membership application process. An applicantusing frontend user interface 112 can initiate and complete anapplication for a trust provided by financial institution 102 via aworkflow corresponding a trust application process. An applicant usingfrontend user interface 112 can initiate and complete an application fora loan provided by financial institution 102 via a workflowcorresponding a loan application process.

In one or more embodiments, each of these different applicationprocesses may further include other phases such as, for example, withoutlimitation, at least one of a qualify phase, a decision phase, or aprocessing phase. In one or more embodiments, these other phases may beautomated such that little to no manual interaction or intervention maybe needed to qualify an application, approve or deny the application,and/or process the application. For example, these other phases may notbe presented to an applicant via frontend user interface 112.

Process tracker 116 may further include a queue manager 126 for managingany number of queues 128 associated with each process type of set ofprocess types 124. For example, each application process type of set ofapplication process types 125 may be associated with one or more queues128. In one or more embodiments, each application of an applicant may beassigned or placed into a particular queue corresponding to theapplication process type for that application. Each queue may representa different “category” of application where the category is based on thelevel of completion of that application, characteristics associated witha reason as to why the application was not completed, and/or othercharacteristics associated with the application. For example, withoutlimitation, a membership application may have been saved for latercompletion and thus only partially complete. The membership applicationmay have been rejected because an applicant failed to comply with themembership rules of financial institution 102, or the application mayhave been rejected because of funding issues. For each one of thesedifferent categories of applications, a respective queue is used totrack and maintain the corresponding one or more applications that fallwithin that category. The category to which an applicant's applicationbelongs may change over time as the applicant progresses through theapplication. Although queues have been described above with respect toapplications, queues may also be used for other types of processes.

Process tracker 116 may include application timeline 130 and subphaseprogression 132 for tracking the progress and status of the applicationprocess for any selected application (e.g., any selected membershipapplication). Application timeline 130 includes a plurality of phases inthe application process. Application timeline 130 may indicate a currentphase of the plurality of phases in the application process based on thecurrent status of the application process. Each of these phases may beassociated with a set of subphases. The user may use backend userinterface 114 to view the set of subphases associated with any phase.For example, in response to a user selecting a phase for viewing,subphase progression 132 identifies the set of subphases within theselected phase. Where a current phase in the application process has aplurality of subphases, subphase progression 132 indicates a currentsubphase of the plurality of subphases based on the current status ofthe application progress.

Process tracker 116 may further include or may be associated withcurrent status section 134. In one or more embodiments, current statussection 134 includes information about at least one of a current phaseof the application process or the current subphase within the currentphase. In one or more embodiments, current status section 134 identifiesa most recent action of an applicant (i.e., the frontend user) who isprogressing through the application process for a selected applicationand identifies whether the applicant has completed the selectedapplication. Current status section 134 may also include controls thatenable the backend user of backend user interface 114 to open theapplication of the applicant via the frontend user interface 112 ofapplication platform 108.

Although application timeline 130, subphase progression 132, and currentstatus section 134 have been described have been described above withrespect to applications, in one or more embodiments, similar elementsmay be included in process tracker 116 for other types of processes.

Framework tool 118 is used to enable customization of the processframework for any one or more of set of process types 124. A frameworkmay define, for example, the foundational elements of a process type orthe entire set of process types 124. A framework, which may be referredto as a core, may define, for example, without limitation, the type ofinformation collected via a process, the type of documentation neededfor the process, requirements for the process, and/or othercharacteristics associated with the process.

For example, framework tool 118 may be used to customize the applicationframework for set of application process types 125 that are presented toan applicant via frontend user interface 112. In such cases, frameworktool 118 may be referred to as an application framework tool. Anapplication framework may be the “core” of one or more applicationprocess types and may define these type of application processes, thetype of documentation needed for the application processes, eligibilityrequirements for the application processes, the types of financialproducts that can be applied for with a given type of applicationprocess, and/or other characteristics or features associated with theapplication processes.

Framework tool 118 allows financial institution 102 to customize theapplication framework based on the individual preferences of financialinstitution 102. In one or more embodiments, the application frameworkis a framework that spans the various types of application processesoffered by financial institution 102. For example, at least a portion ofthe application framework may apply to each type of application processmade available by financial institution 102.

In one or more embodiments, a single framework may serve as the basisfor set of process types 124. In other embodiments, a framework may becustomizable for each of the different process types. In still otherembodiments, a single framework may be used for set of applicationprocess types 125, while one or more other frameworks may be used forother process types.

Workflow experience tool 120 is used to customize the applicant'sexperience progressing through the workflow of the one or more differentapplication processes of set of application process types 125. Forexample, workflow experience tool 120 may be used to customize the textpresented via frontend user interface 112, the types of controls thatare presented via frontend user interface 112, and/or other features.For example, workflow experience tool 120 may be used to customize theworkflow for an application for membership to financial institution 102as the workflow is presented via frontend user interface 112. Thevarious features that may be customized include, but are not limited to,the types of inputs that are solicited from the applicant, the text thatis presented to the applicant, the type of information (e.g., socialsecurity information versus tax ID information) that is required toinitiate the workflow, the various branches in the workflow that may betraversed given an applicant's input during the workflow, and/or othertypes of features.

Theme tool 122 may be used to customize the appearance of applicationplatform 108. For example, theme tool 122 may be used to customize theappearance of frontend user interface 112 of application platform 108.The appearance of frontend user interface 112 includes the “visual look”of frontend user interface 112 with respect to colors, logos, fonts,background graphics, and/or other visual features. Theme tool 122 allowsfinancial institution 102 to, for example, customize frontend userinterface 112 to reflect or match the branding of financial institution.For example, if financial institution 102 undergoes a rebranding inwhich its color scheme is changed, an agent of financial institution 102can use theme tool 122 to quickly and easily modify the appearance offrontend user interface 112 to reflect this rebranding (as opposed to anagent of entity 103 making such modifications).

In one or more embodiments, frontend user interface 112 of applicationplatform 108 and backend user interface 114 of management platform 110may be accessed via a network (e.g., the Internet) for display ondisplay systems. For example, an applicant of financial institution 102may access frontend user interface 112 using a web browser that isdisplayed on first display system 138. First display system 138 mayinclude, for example, the screen of a mobile phone. As another example,an agent of financial institution 102 may access backend user interface114 using a web browser that is displayed on second display system 140.Second display system 140 may include, for example, a display screen ofa laptop, a computer monitor, or some other type of display device. Inone or more embodiments, first display system 138 and second displaysystem 140 are located remotely with respect to each other. Computingsystem 106 (e.g., a server system) may host frontend user interface 112and backend user interface 114. In one or more embodiments, computingsystem 106 is managed by entity 103. In other embodiments, computingsystem 106 is managed by financial institution 102. In still otherembodiments, computing system 106 is managed jointly by entity 103 andfinancial institution 102.

In some embodiments, application system 100 provides solutions toproblems that are unique to the Internet, specifically to the technicalfield of processing an application for a particular membership to afinancial institution and/or a financial product. For example,conventional online application portals do not allow for easycustomization of the membership, products, and design of the frontenduser interface 112. As noted above, financial institutions want to makethe managing and processing of applications for financial products aseasy and efficient as possible so that applicants will want to continuebanking at that particular financial institution. Additionally, creditunions may particularly benefit from a system that can simultaneouslyprocess an application for membership along with an application for oneor more financial product. Being able to simultaneously process anapplication for membership along with an application for one or morefinancial products may reduce the overall computing resources that wouldotherwise be needed to first manage and process the membershipapplication and subsequently manage and process multiple applicationsfor different financial products.

Further, backend user interface 114 provides a technical improvementover conventional technology because the backend user interface 114provides a comprehensive and complete view of the status of themembership application and/or one or more applications for a financialproduct. The backend user interface 114 also provides more granularityregarding the status of the application and/or product. This solvesproblems in the technical field of application monitoring and errordetection by allowing a user monitoring the application from the backendto quickly identify any issues within the application and to identifywhat stage in the application process the applicant is in. By providingthese capabilities in a single backend user interface 114 that is easilynavigable, fewer overall computing resources (e.g., display resources)may be needed.

Backend user interface 114 further enables a financial institution(e.g., credit union) to make edits or customizations for the specificcredit union's application system without requesting third-partyassistance. For example, if a credit union wants to change itsrequirements for membership, change the products it offers, change itsbranding, or etc., the credit union can access backend user interface114 to make these changes without having to engage a third party (e.g.,the initial builder of backend user interface 114). By reducingthird-party reliance, costly delays may be prevented.

Backend user interface 114 also provides a multi-layered approach (usingboth an application timeline and subphase progression) to track thestatus of an application. This multi-layered approach reduces the numberof layers or data that would otherwise need to be utilized in order todiscern the status of an application and improves the efficiency of thecomputer being used to track the status of the application. Using amulti-layered approach to visually summarize the relevant information(e.g., current phase and current subphase) regarding the progress of anapplication in an application timeline and subphase progression, backenduser interface 114 allows the user to quickly discern the progress andcurrent status of the application without the user needing to actuallypull up the application itself, analyze the application data stored inthe application database, and/or perform other time-consuming actionsthat may inefficiently use computing resources. By visually summarizingthe relevant information as describe above, backend user interface 114can display more information to the user in a more easily navigable formusing less visual space, which may improve the functioning of thecomputer. In this manner, using a multi-layered approach that is alsoeasily customizable improves the technical field of online applicationsystems, as well as user interfaces in general.

The illustration of application system 100 in FIG. 1 is not meant toimply physical or architectural limitations to the manner in which anexample embodiment may be implemented. Other components in addition toor in place of the ones illustrated may be used. Some components may beoptional.

FIGS. 2-30 are illustrations of examples of implementations for userinterfaces of application system 100 in FIG. 1 . For example, FIGS.2-22, 24, 26, 28, and 30 are illustrations of one example of animplementation for backend user interface 114 in FIG. 1 in accordancewith one or more embodiments. Further, FIGS. 23, 25, 27, and 29 areillustrations of one example of an implementation for front end userinterface 112 in FIG. 1 in accordance with one or more embodiments.

FIG. 2 is an illustration of a backend user interface in accordance withone or more embodiments. Backend user interface 200 may be displayed ona display system such as, for example, without limitation, seconddisplay system 140 in FIG. 1 . Backend user interface 200, which mayalso be referred to as a management interface, may be one example of animplementation for backend user interface 114 in FIG. 1 . Backend userinterface 200 may be used to manage application platform 108 in FIG. 1and/or the applications initiated and/or completed via applicationplatform 108. Accordingly, FIG. 2 is described with continuing referenceto FIG. 1 .

Backend user interface 200 enables a user (e.g., an agent of financialinstitution 102) to monitor a set of applications for a set of financialproducts provided by financial institution 102, build applicationplatform 108 (e.g., online application platform) for financialinstitution 102, reconfigure application platform 108, and/or otherwisemanage the set of applications, application platform 108, or both.

Backend user interface 200 includes main menu 202 for navigating withinbackend user interface 200. Main menu 202 presents a plurality of menuoptions to the user including, for example, queues option 204, reportsoption 206, administration option 208, configuration option 210, and/orone or more other options. Queues option 204, when expanded, allows auser to view different queues for different application processes. Forexample, when expanded, queues option 204 may include membershipsub-option 212, trust sub-option 214, edit account sub-option 216, loansub-option 218, and/or one or more other sub-options.

Selecting a sub-option from queues option 204 causes one or morecorresponding queues to be displayed. For example, a user selectingmembership sub-option 212 causes backend user interface 200 to presentqueues 220 for membership sub-option 212. Each of queues 220 correspondsto a different category for an application for membership (or“membership application”) to financial institution 102. An applicationmay belong to one or more different queues based on the level ofcompletion of that application, characteristics associated with a reasonas to why the application was not completed, and/or othercharacteristics associated with the application. The different queues220 for membership sub-option 212 may include for example, withoutlimitation: an “all” queue that indicates the total number ofapplications that have been processed using application platform 108; an“in process” queue that indicates the total number of applications inprocess (or in progress); a “decision pending” queue that indicate thenumber of applications where a decision regarding membership is pending;a “decision approved” queue that indicates the number of applicationswhere the decision was made to approve the application; a “decisiondenied” queue that indicates the number of applications where thedecision was made to deny the application; a “failed” queue thatindicates the number of failed applications; an “escalated” queue thatindicates the number of applications escalated (e.g., referred to uppermanagement); an “employees” queue that indicates the number ofapplications belonging to employees of financial institution 102; a“closed” queue that indicates the number of closed applications; and/orone or more other queues.

In this manner, queues 220 allow the backend user interface 200 todifferentiate visually, with ease, between different applicationsdepending on their levels of completion or rather, their respectivestatuses. In some embodiments, each queue may be associated with areminder or alert engine that may trigger an alert to the applicantand/or financial institution 102 that informs of the application'scurrent status. For example, if an application has been placed withinthe “in process” queue, the alert engine may trigger an alert to betransmitted to the applicant on a periodic schedule to remind theapplicant that his/her application needs to be completed in order toengage with financial institution 102. The periodicity or frequency ofthese alerts may be set to any value, such as, but not limited to, anestablished number of hours, days, weeks, months, or even years.

Further, when membership sub-option 212 is selected, backend userinterface 200 also presents membership application section 222.Membership application section 222 presents applications for membershipto financial institution 102 and information about these applications.For example, membership application section 222 may present applicationrecords, with each corresponding to a particular application.Application record 224 is one example of such an application record thatcorresponds to a particular application for membership to financialinstitution 102. A user may select application record 224 to view moredetailed information about the corresponding application and/or a statusof the application. Accordingly, a selection of an application recordsuch as application record 224 is a selection of the correspondingapplication.

The total number of applications listed in membership applicationsection 222 may be reduced by filtering using queues 220. For example,selecting the “in process” queue may cause backend user interface 200 todisplay in membership application section 222 only those applicationsthat are in process. Selecting the “decision denied” queue may causebackend user interface 200 to display in membership application section222 only those applications where membership was denied.

New application control 226 allows a user to manually initiate a newapplication and thereby cause a new application record to be displayedin membership application section 222. In one or more embodiments, newapplication control 226, when selected, directs the user to a frontenduser interface (e.g., frontend user interface 112) of applicationplatform 108 in FIG. 1 .

Although queues 220, membership application section 222, and newapplication control 226 are shown for membership sub-option 212 in FIG.2 , similar elements may be similarly presented in backend userinterface 200 when trust sub-option 214, edit account sub-option 216, orloan sub-option 218 is selected by the user.

As noted above, main menu 202 also includes reports option 206,administration option 208, and configuration option 210. Reports option206 may allow a user (e.g., an agent of financial institution 102) tocreate, edit, print, and/or otherwise manage one or more reports. Thesereports may provide different types of information about theapplications being processed via application platform 108 in FIG. 1 .Administration option 208 may allow a user to perform administrativefunctions with respect to application platform 108, management platform110, or both. For example, administration option 208 may allow the userto manage the security for and/or access to application platform 108,management platform 110, or both. Configuration option 210 may allow auser to customize application platform 108 by, for example, customizingfrontend user interface 112 of application platform 108.

FIG. 3 is another illustration of backend user interface 200 from FIG. 2in accordance with one or more embodiments. Backend user interface 200may present process tracker 300, current status section 302, or bothwithin application section 304 in response to a user (e.g., an agent offinancial institution 102) selecting an application record (e.g.,application record 224) presented within membership application section222 in FIG. 2 . Application section 304 may be, for example, a sectionof backend user interface 200 designated for displaying informationabout the selected application record.

Process tracker 300 may include or be associated with current statussection 302. Process tracker 300 may be one example of an implementationfor process tracker 116 in FIG. 1 . Current status section 302 may beone example of an implementation for current status section 134 in FIG.1 .

Process tracker 300 allows the user to get a snapshot view of thecurrent status of the application process for the selected application.Process tracker 300 is described in greater detail in FIGS. 6-9 below.Current status section 302 may provide a brief note regarding thecurrent status of the application. In one or more embodiments, currentstatus section 302 identifies a most recent action of the applicant whois progressing through the application process for the selectedapplication and whether the applicant has completed the selectedapplication.

Within application section 304, backend user interface 200 may furtherpresent application process snapshot 306. Application process snapshot306 may provide a brief overview of the application process for theselected application. This brief overview may include, for example, anidentifier for the application (or applicant), a status regarding adecision about the application, a date and/or timestamp for when datawas last received for the application, an indication of how long it hasbeen since the application was last active, a total amount that has beendeposited by the applicant, and/or other types of information.

Application section 304 may further include, for example, applicationdetails navigator 308. Applicant details navigator 308 provides a wayfor the user to navigate through the various sections of informationprovided within application section 304. For example, applicationdetails navigator 308 allows the user to “jump to” different portions ofthe information presented in application section 304, which may be in,for example, scrollable form. As noted by applicant details navigator308, application section 304 may further provide application information310, primary applicant information 312, and/or other types ofinformation (e.g., products information, funding information, applicantcard information, application documents information) related to theselected application.

Backend user interface 200 may further includes notes section 314. Notessection 314 allows the user to create and/or view notes regarding theselected application. These notes may be created by the user (e.g.,agent of financial institution 102), the system (which is managementplatform 110), or both.

Backend user interface 200 may further include escalate control 316,close control 318, and email control 320. Escalate control 316 may beselected by the user to escalate the selected application. Escalationmay include, for example, but is not limited to, sending the applicationto upper management, increasing a priority of the application, and/orflagging the application as important. Close control 318 may be selectedto close the selected application. Closing the application may, in somecases, close the application and prevent the applicant from inputtingany further data via frontend user interface 112 of application platform108. In some embodiments, closing the application may be selected afteran application has been denied or approved to indicate that theapplication has been fully addressed. Email control 320 may be selectedby the user to generate a customized email. This customized email may besent to the applicant, another agent of financial institution 102, orsome other person or entity.

FIG. 4 is another illustration of backend user interface 200 from FIGS.2 and 3 in accordance with one or more embodiments. In FIG. 4 , adifferent portion of information is shown in application section 304.For example, more of primary applicant information 312 can be viewed.Primary applicant information 312 may include, for example, signature400 of the applicant. Signature 400 may be a digital signature that waseither uploaded by the applicant via frontend user interface 112 ofapplication platform 108 or generated via frontend user interface 112 ofapplication platform 108.

In one or more embodiments, signature 400 is stored and used, withauthorization by the applicant, by management platform 110 for one ormore documents that are generated via the application process requiringthe applicant's signature. For example, once an application is completedonline, a set of financial disclosure documents may need to be generatedwith the applicant's signature. Rather than the applicant having toenter his or her signature for each and every financial disclosuredocument, management platform 110 may simply insert signature 400 intoeach of the financial disclosure documents if the applicant has providedsuch authorization. This saves time and effort as compared to electronicplatforms in which an applicant must separately enter a signature foreach document requiring a signature.

Further, by including signature 400 in primary applicant information312, the user (e.g., agent of financial institution 102) of backend userinterface 114 may be able to review signature 400 and confirm whether ornot signature 400 is sufficient (e.g., sufficiently legible, etc.).

FIG. 5 is another illustration of backend user interface 200 from FIGS.2-4 in accordance with one or more embodiments. In FIG. 5 , yet anotherportion of information is shown in application section 304. For example,products information 500, funding information 502, applicant cardinformation 504, and application documents information 506 can beviewed. As shown in FIG. 5 , the display of products information 500,funding information 502, applicant card information 504, and applicationdocuments information 506 within application section 304 cause applicantdetails navigator 308 to graphically indicate to the user that these arethe types of information being shown. For example, graphical indicators508 are used within applicant details navigator 308 to denote thatproducts information 500, funding information 502, applicant cardinformation 504, and application documents information 506 are currentlydisplayed within application section 304.

FIG. 6 is an illustration of an enlarged view of process tracker 300 andcurrent status section 302 of application section 304 within backenduser interface 200 from FIG. 3 in accordance with one or moreembodiments. As depicted, process tracker 300 includes applicationtimeline 600 that includes plurality of phases 602. Application timeline600 may be one example of an implementation for application timeline 130in FIG. 1 . Each of plurality of phases 602 may be a different phaseassociated with the application process for an application (e.g.,application for membership to financial institution 102). Plurality ofphases 602 may include, for example, workflow phase 604, qualify phase606, decision phase 608, and processing phase 610.

Based on a determination of the current status of the applicationprocess corresponding to a selected application (e.g., selected via theselection of an application record in membership application section 222in FIG. 2 ) using the application data associated with the selectedapplication, the current phase of plurality of phases 602 for theselected application may be determined. In one or more embodiments,backend user interface 200 displays a graphical indication (e.g.,graphical indicator 612) of this current phase. Graphical indicator 612may include, for example, without limitation, a certain color, a symbol,a graphical icon, an animation, or some other type of visual indicatorfor indicating the current phase.

Each of plurality of phases 602 may itself be comprised of one or moresubphases. Process tracker 300 may include a subphase progression thatincludes the one or more subphases for a default phase of plurality ofphases 602 or for a selected phase that is selected by the user. In someembodiments, the default phase is the current phase.

In FIG. 6 , workflow phase 604 is the selected phase and process tracker300 includes workflow subphase progression 614 corresponding to workflowphase 604. Workflow subphase progression 614 may be one example of animplementation for subphase progression 132 in FIG. 1 . Workflowsubphase progression 614 includes plurality of subphases 616. Each ofplurality of subphases 616 corresponds to a different step(s) inworkflow phase 604. Plurality of subphases 616 may include, for example,without limitation, agreements subphase 618, account subphase 620,products subphase 622, applicants subphase 624, review subphase 626,funding subphase 628, authentication subphase 630, and confirmationsubphase 632.

Graphical indicators may be used to indicate which of plurality ofsubphases 616, if any, has been completed, which of plurality ofsubphases 616 is in progress, and which of plurality of subphases 616,if any, has yet to be initiated. For example, graphical indicator 634may be used to indicate that agreements subphase 618 has been completed.Graphical indicator 634 may include, a color, a symbol, a graphicalicon, an animation, or some other type of visual indicator thatdistinguishes the corresponding subphase as “completed.”

Graphical indicator 636 may be used to indicate that review subphase 626is in progress. Graphical indicator 636 may include, a color, a symbol,a graphical icon, an animation, or some other type of visual indicatorthat distinguishes the corresponding subphase as “in progress.” Further,graphical indicator 638 may be used to indicate that authenticationsubphase 630 has yet to be initiated. Graphical indicator 638 mayinclude, a color, a symbol, a graphical icon, an animation, or someother type of visual indicator that distinguishes the correspondingsubphase as “yet to be initiated.”

In one or more embodiments, current status section 302 includesinformation about the current phase of plurality of phases 602, thecurrent subphase of plurality of subphases 616, or both. In one or moreembodiments, current status section 302 identifies a most recent actionof the applicant who is progressing through the application process forthe selected application and whether the applicant has completed theselected application.

In one or more embodiments, current status section 302 includes a briefindication of the status of the application with respect to the selectedphase of plurality of phases 602. For example, when workflow phase 604is selected, current status section 302 may provide information aboutthe status of the workflow for the selected application. In someembodiments, current status section 302 includes open workflow control640 and reminder control 642. The user may select open workflow control640 to open the current workflow for the selected application. Forexample, a selection of open workflow control 640 may open an instanceof frontend user interface 112 of application platform 108 with theapplication data for the selected application already populated.Accordingly, the user may be able to view, edit, and/or otherwisefacilitate traversal through the workflow. The user may select remindercontrol 642 to trigger the sending of a reminder (e.g., a reminderemail, reminder text message, reminder alert, etc.) to the applicantthat the workflow is in progress and still needs to be completed by theapplicant.

FIG. 7 is an illustration of an enlarged view of process tracker 300 andcurrent status section 302 of application section 304 within backenduser interface 200 from FIG. 3 in accordance with one or moreembodiments. In one or more embodiments, a new user input may bereceived via backend user interface 200 that selects, via theapplication timeline 600, a different (e.g., a non-current) phase thanworkflow phase 604 of plurality of phases 602. Backend user interface200 may remove workflow subphase progression 614 that was previouslydisplayed in FIG. 6 and display a new subphase progression for the newlyselected phase.

When the newly selected phase of plurality of phases 602 of applicationtimeline 600 is qualify phase 606, qualify subphase progression 700 isdisplayed within process tracker 300. Qualify subphase progression 700includes plurality of subphases 702. Each of plurality of subphases 702may include one or more steps for determining whether the applicantqualifies for membership to financial institution 102.

Plurality of subphases 702 may include, for example, without limitation,identity verification 704, OFAC 706, qualifile 708, and credit report710. Identity verification 704 may include one or more steps forverifying the identity of the applicant. OFAC 706 may include one ormore steps for determining whether the applicant can be found on a watchlist maintained by the Office of Foreign Assets Control (“OFAC”).Qualifile 708 may include one or more steps for determining theapplicant's QualiFile® score and whether or not the QualiFile® scoresatisfies a set of criteria for membership qualification. Credit report710 may include one or more steps for retrieving one or more creditreports for the applicant and/or determining whether or not the one ormore credit reports satisfy a set of criteria for membershipqualification.

In FIG. 7 , current status section 302 has been updated based on theselection of qualify phase 606. Current status section 302 providesinformation about the status of the application with respect to qualifyphase 606. For example, current status section 302 indicates that anidentity verification, which is the first step(s) in qualify phase 606,still needs to be performed for the selected application.

FIG. 8 is an illustration of an enlarged view of process tracker 300 andcurrent status section 302 of application section 304 within backenduser interface 200 from FIG. 3 in accordance with one or moreembodiments. In FIG. 8 , the selected phase of plurality of phases 602of application timeline 600 is decision phase 608. The selection ofdecision phase 608 causes decision subphase progression 800 to bedisplayed within process tracker 300. Decision subphase progression 800includes a single subphase, the decision subphase 802.

The selection of decision phase 608 further causes current statussection 302 to be updated. Current status section 302 providesinformation about the status of the application with respect to decisionphase 608. For example, current status section 302 indicates that adecision cannot yet be generated based on the status of the application,and if a decision is necessary, a manual decision is needed. Currentstatus section 302 further allows this manual decision to be made.Current status section 302 makes this type of manual decision-makingeasy, fast, and efficient because the user does not need to navigate toanother window or section of backend user interface 200 in order toquickly approve or deny the application.

FIG. 9 is an illustration of an enlarged view of process tracker 300 andcurrent status section 302 of application section 304 within backenduser interface 200 from FIG. 3 in accordance with one or moreembodiments. In FIG. 9 , the selected phase of plurality of phases 602of application timeline 600 is processing phase 610. The selection ofprocessing phase 610 causes processing subphase progression 900 to bedisplayed within process tracker 300.

Processing subphase progression 900 includes plurality of subphases 902.Each of plurality of subphases 902 includes one or more steps that arepart of the processing of the application after a decision has been madeabout the application. Plurality of subphases 902 may include, forexample, without limitation, funding subphase 904, post to core subphase906, documents subphase 908, and/or one or more other subphases. Theselection of processing phase 610 further causes current status section302 to be updated. Current status section 302 provides information aboutthe status of the application with respect to processing phase 610. Forexample, current status section 302 indicates that the applicant isstill awaiting funding as other steps in the application process haveyet to be completed.

FIG. 10 is an illustration of backend user interface 200 from FIGS. 3-5in accordance with one or more embodiments. Primary applicantinformation 312 includes action icon 1000 that can be selected. Aselection of action icon 1000 may cause action listing 1002 to begenerated. Action listing 1002 may identify one or more actions thathave been taken or performed as part of the application process for theselected application. For example, action listing 1002 may identify anyreports that have been generated, any documents that have been uploaded,any identity verifications that have been performed, any credit reportsthat have been pulled, and/or other types of actions. Action listing1002 may also include a date and/or timestamp for any action included inaction listing 1002.

Action icon 1000 and action listing 1002 provide an efficient way ofpresenting this information about the actions taken or performed withoutthe user having to navigate to another window or section of backend userinterface 200. For example, in some embodiments, the actions identifiedin action listing 1002 may include those taken or performed withindifferent phases of plurality of phases 602 of application timeline 600.

FIG. 11 is an illustration of backend user interface 200 from FIG. 2 inaccordance with one or more embodiments. In FIG. 11 , administrationoption 208 has been expanded. Administration option 208, when expanded,includes a plurality of sub-options that include users sub-option 1102,roles sub-option 1104, access control sub-option 1106, global settingssub-option 1108, and/or one or more other sub-options.

Users sub-option 1102 is currently selected. The selection of userssub-option 1102 causes user listing 1110 to be presented within backenduser interface 200. User listing 1110 identifies the various useraccounts for those users who can access management platform 110 andthereby backend user interface 200. Any one of the user accountsidentified in user listing 1110 may be selected to allow more detailedinformation for that user account to be viewed and/or edited.

For example, the selection of user account 1112 causes information aboutuser account 1112 to be displayed within user information section 1114.User information section 1114 provides information about thecorresponding user account, the various permissions and/or capabilitiesfor the user account, a name for the user account, a login identifierfor the user account, contact information (e.g., email) for the useraccount, a picture for the user account, and/or other information. Userinformation section 1114 also allows the details for a user account tobe edited.

FIG. 12 is an illustration of backend user interface 200 from FIG. 11 inaccordance with one or more embodiments. In FIG. 12 , roles sub-option1104 has been selected. The selection of roles sub-option 1104 causesrole listing 1200 to be presented within backend user interface 200.Role listing 1200 identifies the various types of roles that may be heldby a given user. Each of these roles may be assigned differentpermissions and/or capabilities with respect to management platform 110,application platform 108, or both.

For example, role 1202 identified in role listing 1200 may be selected.This selection causes information about role 1202 to be displayed withinrole definition section 1204. Role definition section 1204 may includepermissions 1206 and active controls 1208. Permissions 1206 identify thevarious types of permissions that could be assigned to a given role.Active controls 1208 are used to determine which of those permissions toactivate and which to make inactive or deactivate.

FIG. 13 is an illustration of backend user interface 200 from FIGS.11-12 in accordance with one or more embodiments. In FIG. 13 , anotherportion of role definition section 1204 is viewed. In addition topermissions 1206 and active controls 1208, role definition section 1204may further include an assignments section 1300. Assignments section1300 identifies those user account that have been assigned to thecurrently selected role.

FIG. 14 is an illustration of backend user interface 200 from FIGS.11-13 in accordance with one or more embodiments. In FIG. 14 , accesscontrol sub-option 1106 has been selected. The selection of accesscontrol sub-option 1106 causes access control menu 1400 to be displayed.A user may select any of the options provided in access control menu1400 to limit the access of applicant, financial institution agents,and/or other types of users to management platform 110 via backend userinterface 200, application platform 108 via frontend user interface 112,or both.

In one or more embodiments, access control menu 1400 includes thefollowing options: IP address blacklist, tax ID blacklist, phone numberblacklist, email blacklist, and an administrator (e.g., OAdmin) IPaddress whitelist. The different blacklists limit access, while thewhitelist allows access. A selection of one of the options within accesscontrol menu 1400 causes the corresponding “list” (e.g., blacklist orwhitelist) to be displayed within access control information section1402. These lists may then be modified within access control informationsection 1402. For example, a particular IP address, tax ID, phonenumber, or email may be added to the respective blacklist to preventthat particular IP address, tax ID, phone number, or email,respectively, from gaining access to application platform 108,management platform 110, or both. As another example, a particular IPaddress may be added to the administrator IP address whitelist to allowa user having that particular IP address administrative level access toapplication platform 108, management platform 110, or both.

FIG. 15 is an illustration of backend user interface 200 from FIGS.11-14 in accordance with one or more embodiments. In FIG. 15 , globalsettings sub-option 1108 has been selected. The selection of globalsettings sub-option 1108 causes global settings navigator 1500 to bedisplayed. A user may navigate to any of the options identified inglobal settings navigator 1500 by selecting such an option or scrollingwithin settings section 1502 to customize one or more global settingsfor application platform 108, management platform 110, or both. Settingssection 1502 includes logins and password section 1504 that allows theuser to modify the requirements for logins and/or passwords needed foraccess to application platform 108, management platform 110, or both.

FIG. 16 is an illustration of backend user interface 200 from FIG. 15 inaccordance with one or more embodiments. In FIG. 16 , a differentportion of settings section 1502 is shown. Settings section 1502includes organization details section 1600 and license section 1601. Auser may use organization details section 1600 to modify details aboutfinancial institution 102. Such details may include, but are not limitedto, a name, a short name, a routing number, a location, contactinformation, and/or other types of information.

License section 1601 may provide details about the license of managementplatform 110 to financial institution 102. For example, license section1601 may identify the license key 1602 that provides financialinstitution 102 with authorized access to management platform 110 andthereby backend user interface 200. License section 1601 may alsoinclude attribute information 1604 about the license. Such attributeinformation may identify, for example, the types of workflows or modulesthat have been enabled within the version of backend user interface 200licensed to financial institution 102.

FIG. 17 is an illustration of backend user interface 200 from FIG. 2 inaccordance with one or more embodiments. In FIG. 17 , configurationoption 210 has been expanded. Configuration option 210, when expanded,includes a plurality of sub-options that include framework sub-option1702 (“core”), workflow sub-option 1704, theme sub-option 1706, and/orone or more other sub-options.

Framework sub-option 1702, which may also be referred to as a coresub-option, is currently selected. The selection of framework sub-option1702 presents framework tool 1707 to the user that the user can then useto customize the application framework of application platform 108.Framework tool 1707 may be one example of an implementation forframework tool 118 in FIG. 1 . For example, framework tool 1707 mayinclude framework section 1708, selected feature section 1710, anddetails section 1712.

Framework section 1708, which may be also referred to as a core section,includes plurality of framework features 1714, each of which may becustomizable. Plurality of framework features 1714 may include, forexample, account type 1716, which controls the types of accounts (e.g.,membership accounts) that can be applied for via application platform108. When account type 1716 is selected, selected feature section 1710may display a list of predefined account types. The user may select aset of account types from the list of predefined account types. Forexample, the user may deselect (e.g., deactivate) an account typeincluded in a default set of account types, select (e.g., activate) anew account type from the list of predefined account types not includedin the default set of account types, or both. The user may add a newaccount type to the list of predefined account types and, for example,select (e.g., activate) the new account type. Details about each of thedifferent account types may be customized in details section 1712.

FIG. 18 is an illustration of backend user interface 200 from FIG. 17 inaccordance with one or more embodiments. In FIG. 18 , document type 1800of plurality of framework features 1714 has been selected. Document type1800 controls the types of documents that can be uploaded to, importedinto, and/or generated using application platform 108. The differenttypes of document types already supported may be shown in selectedfeature section 1710. Details about a given document may be viewedwithin details section 1712.

The user may, for example, create a new document type using add control1802, which creates a new document type record, the details of which canbe customized within details section 1712. For example, a user mayupload a PDF template of a document via details section 1712. When thePDF template of the document has a format that is compatible withmanagement platform 110, management platform 110 may be able toseamlessly incorporate the document and associate various fields withinthe document with the database housing application data.

FIG. 19 is an illustration of backend user interface 200 from FIGS.17-18 in accordance with one or more embodiments. In FIG. 19 , productgroup (which may be also referred to as share group) 1900 of pluralityof framework features 1714 has been selected. Product group 1900controls the different groups (or categories) of products that may beoffered via application platform 108. Each product group or category mayitself include different types of products.

The different types of product groups available may be shown in selectedfeature section 1710. As one example, the product groups may include asavings group, a checking group, a certificate of deposit (CD) group, amoney market group, and/or one or more other types of product groups. Auser may select a set of product groups from the list of predefinedproduct groups shown in selected feature section 1710. The user may, forexample, modify a default set of product groups by deselecting (e.g.,deactivating) a product group of the default set of product groups,selecting (e.g., activating) a product group in the list of predefinedproduct groups that was not already present in the default set ofproduct groups, or both. The user may, for example, add a new productgroup, providing details about the new product group in details section1712. Details section 1712 may also be used to modify the details of oneor more product groups.

FIG. 20 is an illustration of backend user interface 200 from FIGS.17-19 in accordance with one or more embodiments. In FIG. 20 , producttype (which may be also referred to as share type) 2000 of plurality offramework features 1714 has been selected. Product type 2000 controlsthe different types of financial products that may be offered viaapplication platform 108. Each product type may, for example, belong toa corresponding one of the product groups described above with respectto FIG. 19 .

The different types of products available may be shown in selectedfeature section 1710. As one example, the product types may include oneor more savings accounts, one or more checking accounts, one or moremoney market accounts, one or more CDs, one or more loans, one or moretrusts, and/or one or more other types of products.

A user may select a set of financial products from the list ofpredefined product types shown in selected feature section 1710. Thelist of predefined product types may include, for example, at leastthree selected from a group consisting of a checking account, a savingsaccount, a money market account, a CD, a loan, or a trust. The user may,for example, modify a default set of financial products by deselecting(e.g., deactivating) a financial product of the default set of financialproducts, selecting (e.g., activating) a financial product in the listof predefined product groups that was not already present in the defaultset of financial products, or both. The user may, for example, add a newfinancial product, providing details about the new financial product indetails section 1712. Details section 1712 may also be used to modifythe details of one or more financial products.

FIG. 21 is an illustration of backend user interface 200 from FIGS.17-20 in accordance with one or more embodiments. In FIG. 21 , thirdparty integration 2100 of plurality of framework features 1714 has beenselected. Third party integration 2100 controls the different types ofthird party services that may be accessible or set up for communicationwith application platform 108. The different types of third partyservices available may be shown in selected feature section 1710. Thethird party services may include, for example, but are not limited to,various types of credit reporting agencies, payment agencies, identityverification services, and/or other types of third party services. Inone or more embodiments, a user may deselect and/or select various thirdparty services and/or modify the details of various third party servicesto customize a default set of third party services selected from a listof predefined third party services. In one or more embodiments, the usermay add a new third party service and the corresponding details for thatthird party service.

FIG. 22 is an illustration of backend user interface 200 from FIG. 17 inaccordance with one or more embodiments. In FIG. 22 , workflowsub-option 1704, which may also be referred to as a workflow experiencesub-option, is currently selected. The selection of workflow sub-option1704 presents workflow experience tool 2200 to the user that the usercan then use to customize the workflow that is presented to an applicantvia frontend user interface 112 of application platform 108. Workflowexperience tool 2200 may be one example of an implementation forworkflow experience tool 120 in FIG. 1 .

Workflow experience tool 2200 allows the user to customize anapplicant's workflow experience via frontend user interface 112. Forexample, workflow experience tool 2200 allows the user to customize thevisual cues, text, prompts, fields, and/or other pieces of informationthat direct an applicant through a workflow of an application processvia frontend user interface 112 with respect to the various subphases ofthat workflow.

Workflow experience tool 2200 may include, for example, withoutlimitation, workflow selection control 2202, subphase navigator 2204,common element navigator 2206, subphase experience section 2208, and/orsubphase details section 2210. Workflow selection control 2202 allowsthe user to select the workflow type (e.g., membership, trust, loan,account editing, etc.). For the selected workflow type, subphasenavigator 2204 allows the user to navigate to the different subphasescorresponding to the workflow. Common element navigator 2206 allows theuser to navigate to various elements that are common to the differentworkflow types. Such common elements may include, for example, a contactwidget that appears in frontend user interface 112, a footer thatappears in frontend user interface 112, a loading animation that appearsin frontend user interface 112, and/or one or more other elements.

Subphase experience section 2208 provides a general architecturalpreview of the different elements specific to a corresponding subphase.For example, the user may select a subphase via subphase navigator 2204or may scroll through subphase experience section 2208 to a particularsubphase to view the different elements presented in frontend userinterface 112 for that subphase. The user may then select any element orelement group to view the details of that element or element group insubphase details section 2210. The user may modify these details (e.g.,text, font, alignment, graphics, etc.) associated with the element orelement group within subphase details section 2210. In this manner, eachsubphase of a workflow may be fully customizable.

In FIG. 22 , agreements subphase 2212 has been selected forcustomization. In particular, headers 2214 of agreements subphase 2212has been selected for customization. The user may modify the details forheaders 2214 within subphase details section 2210 to change thecorresponding display of headers in frontend user interface 112 for thecorresponding agreements subphase of the workflow for a membershipapplication.

FIG. 23 is an illustration of a frontend user interface in accordancewith one or more embodiments. Frontend user interface 2300 may be oneexample of an implementation for frontend user interface 112 in FIG. 1 .Frontend user interface 2300 is currently displaying page 2302 thatcorresponds to agreements subphase 2304. Header section 2306 is oneexample of the type of header(s) that may be customized via headers 2214in workflow experience tool 2200 in FIG. 22 .

FIG. 24 is an illustration of backend user interface 200 from FIG. 22 inaccordance with one or more embodiments. In FIG. 24 , account subphase2400 has been selected for customization. In particular, progress menu2402 of account subphase 2400 has been selected for customization. Theuser may modify the details for progress menu 2402 within subphasedetails section 2210 to change the corresponding display of a progressmenu in frontend user interface 112 for the corresponding accountsubphase of the workflow for a membership application.

In some embodiments, workflow experience tool 2200, which may includesubphase navigator 2204, of the backend user interface 200simultaneously displays each subphase of the workflow and highlightswhich subphase that the user has started, displayed, and/or completed.

For example, progress menu 2402 of backend user interface 200 maysimultaneously display each subphase of the workflow and indicate whichsubphase(s) that the user has started, displayed, and/or completed. Forexample, progress menu 2402 may graphically indicate (e.g., via color,highlighting, shading, pattern, a symbol, and/or some other type ofgraphical or visual indicator) the subphase that is being currentlydisplayed on frontend user interface 2300, the current subphase that isbeing engaged by the applicant, the subphase most recently accessed bythe applicant, etc. For example, progress menu 2402 may graphicallyindicate (e.g., via color, highlighting, shading, pattern, a symbol,and/or some other type of graphical or visual indicator) the subphasethat is being currently displayed on frontend user interface 2300, thecurrent subphase that is being engaged by the applicant, the subphasemost recently accessed by the applicant, etc. In FIG. 24 , progress menu2402 graphically indicates that an account subphase is the most recentsubphase accessed by the applicant. Progress menu 2402 may furthergraphically distinguish other subphases that have been previouslydisplayed to or engaged by the applicant, whether or not these othersubphases are earlier or later than accounts subphase according toprogress menu 2402, from subphases that have yet to be displayed to orengaged by the applicant. In some embodiments, progress meu 2402 listsevery subphase that is to be completed to finish the membershipapplication and/or application for a financial product.

In one or more embodiments, progress menu 2402 of frontend userinterface 2300 provides a technical improvement by visually linking theuser to where the applicant is in the application process, visuallylinking the user to how many more subphases remain to be completed bythe applicant, and visually linking backend user interface 200 tofrontend user interface 2300.

FIG. 25 is an illustration of frontend user interface 2300 from FIG. 23in accordance with one or more embodiments. Frontend user interface 2300is currently displaying page 2500 that corresponds to account subphase2502. Progress menu 2504 is one example of the type of progress menuthat may be customized via progress menu 2402 in workflow experiencetool 2200 in FIG. 24 .

The progress menu 2504 of frontend user interface 2300 maysimultaneously display each subphase of the workflow and indicate whichsubphase(s) that the applicant has started, displayed, and/or completed.For example, progress menu 2504 may graphically indicate (e.g., viacolor, highlighting, shading, pattern, a symbol, and/or some other typeof graphical or visual indicator) the subphase that is being currentlydisplayed on frontend user interface 2300. In FIG. 25 , progress menu2504 graphically indicates that account subphase 2502 is the currentsubphase being displayed. Progress menu 2504 further graphicallydistinguishes other subphases (e.g., such as agreements subphase 2304)that have been previously displayed to or engaged by the applicant,whether these other subphases are earlier or later than accountssubphase 2502 according to progress menu 2504, from subphases that haveyet to be displayed to or engaged by the applicant. In some embodiments,progress meu 2504 lists every subphase that is to be completed to finishthe membership application and/or application for a financial product.

In one or more embodiments, progress menu 2504 of frontend userinterface 2300 provides a technical improvement over conventionalsystems by visually linking the user to where the applicant is in theapplication process, visually linking the applicant to how many moresubphases remain to be completed, and visually linking the frontend userinterface 2300 to the backend user interface 200 (e.g., such as toprogress menu 2402 in FIG. 24 ).

FIG. 26 is an illustration of backend user interface 200 from FIG. 22 inaccordance with one or more embodiments. In FIG. 26 , products subphase2600 has been selected for customization. In particular, headers 2602 ofproducts subphase 2600 has been selected for customization. The user maymodify the details for headers 2602 within subphase details section 2210to change the corresponding display of one or more headers in frontenduser interface 112 for the corresponding products subphase of theworkflow for a membership application.

FIG. 27 is an illustration of frontend user interface 2300 from FIG. 23in accordance with one or more embodiments. Frontend user interface 2300is currently displaying page 2700 that corresponds to products subphase2702. Header section 2704 is one example of the type of header(s) thatmay be customized via headers 2602 in workflow experience tool 2200 inFIG. 26 .

FIG. 28 is an illustration of backend user interface 200 from FIG. 22 inaccordance with one or more embodiments. In FIG. 28 , funding subphase2800 has been selected for customization. In particular, funding details2802 for funding subphase 2800 has been selected for customization. Theuser may modify the various details of funding details 2802 withinsubphase details section 2210 to change the corresponding display offunding details in frontend user interface 112 for the correspondingfunding subphase of the workflow for a membership application.

FIG. 29 is an illustration of frontend user interface 2300 from FIG. 23in accordance with one or more embodiments. Frontend user interface 2300is currently displaying page 2900 that corresponds to funding subphase2902. Funding details section 2904 includes details that are one exampleof the type of details that may be customized via funding details 2802in workflow experience tool 2200 in FIG. 28 .

FIGS. 22, 24, 26, and 28 illustrate examples of the types of elements ofa workflow experience that can be customized. However, the embodimentsdescribed herein enable other elements to be customized in a similarmanner.

FIG. 30 is an illustration of backend user interface 200 from FIG. 17 inaccordance with one or more embodiments. In FIG. 30 , theme sub-option1706 is currently selected. The selection of theme sub-option 1706presents theme tool 3000 to the user that the user can then use tocustomize the theme that is presented to an applicant via frontend userinterface 112 of application platform 108. Theme tool 3000 may be oneexample of an implementation for theme tool 122 in FIG. 1 .

Theme tool 3000 allows the user to customize the appearance of frontenduser interface 112 of application platform 108. For example, theme tool3000 allows the user to customize various characteristics (e.g., colors,logos, font, etc.) that form the overall appearance (e.g., “look andfeel”) of frontend user interface 112 of application platform 108.

Theme tool 3000 includes characteristic modifier 3002, preview section3004, look and feel navigator 3006, common elements navigator 3008, andmodule options navigator 3010. Characteristic modifier 3002 includesvarious characteristics of the appearance that can be modified. Thesecharacteristics may include, for example, main colors (e.g., primarycolor, secondary color, accent color, etc.), other colors (e.g.,background color, body text color, box background color, borders color,success color, error color, etc.), logo, fonts, and/or other types ofcharacteristics. Each of these characteristics may be associated with avalue that can be customized. The value for a characteristic that is acolor may be, for example, without limitation, a hex code for the color.The value for a characteristic that is a font may be, for example, anidentification of a font type. The value for a characteristic that is alogo may be, for example, without limitation, a graphic, an importedfile that includes the graphic, or some other type of logorepresentation.

Background color 3012 is one example of a characteristic that can bemodified using characteristic modifier 3002 by changing its value viavalue selector 3014. Preview section 3004 provides a preview of theappearance of frontend user interface 112 (e.g., frontend user interface2300 in FIGS. 23, 25, 27 , and/or 29) based on the values forcharacteristics selected in characteristic modifier 3002.

Characteristic modifier 3002 may be scrollable. In one or moreembodiments, the user may use look and feel navigator 3006, commonelements navigator 3008, and module options navigator 3010 to navigateto the different corresponding groupings of characteristics withincharacteristic modifier 3002.

In one or more embodiments, theme tool 3000 includes save control 3016and publish control 3018. Save control 3016 allows the user to save anychanges without those changes being officially implemented in frontenduser interface 112. Publish control 3018 allows the user to both saveand publish any changes such that those changes are implemented insubstantially real-time in frontend user interface 112.

Theme tool 3000 allows the user (e.g., agent of financial institution102) to customize the appearance of frontend user interface 112 suchthat the appearance corresponds with a branding of financialinstitution. Further, financial institution 102 may use theme tool 3000to customize the appearance of frontend user interface 112 wheneverfinancial institution 102 undergoes a rebranding.

The illustrations of backend user interface 200 in FIGS. 2-22, 24, 26,28, and 30 and frontend user interface 2300 in FIGS. 23, 25, 27, and 29are not meant to imply any physical or architectural limitations to themanner in which these user interfaces may be implemented. In one or moreembodiments,

FIG. 31 is a flowchart of a process for monitoring a set of applicationsfor a set of financial products provided by a financial institution inaccordance with one or more embodiments. Process 3100 may be implementedusing, for example, application system 100 in FIG. 1 . In one or moreembodiments, process 3100 may be implemented using management platform110 of application system 100 in FIG. 1 .

Step 3102 includes displaying a set of applications via a managementplatform on a display system, wherein each application of the set ofapplications is associated with application data stored in anapplication database. The management platform, which may be, forexample, management platform 110 in FIG. 1 , may display the set ofapplications using a backend user interface (e.g., backend userinterface 114 in FIG. 1 ), which may be also referred to as a managementinterface. The application database may be, for example, database 111 inFIG. 1 .

In one or more embodiments, the set of applications is displayed via thebackend user interface on a display system that is owned, operated by,and/or otherwise in use by a financial institution such as financialinstitution 102 in FIG. 1 . In one embodiment, this display system(e.g., the screen of a mobile device, laptop, desktop, tablet, etc.) maybe located remotely (with respect to the application database, which maybe owned, operated by, and/or otherwise in use by an entity such asentity 103 in FIG. 1 . In other embodiments, the display system may belocated locally with respect to the application database. The managementplatform is in communication with the application database and capableof retrieving the application data from the application database.

Step 3104 includes receiving user input identifying a selectedapplication from the set of applications. The user input may be enteredby, for example, an agent of the financial institution. The user inputmay identify the selected application by, for example, withoutlimitation, selecting an application record (e.g., application record224 in FIG. 2 ) displayed in the backend user interface.

Step 3106 includes determining a current status of an applicationprocess corresponding to the selected application using the applicationdata associated with the selected application. The current status may bedetermined based on, for example, whether the application is inprogress, whether the application has completed a qualification process,whether a decision has been made regarding the application (e.g.,approval/denial), whether the application has been processedpost-decision, and/or other information. In one or more embodiments, thecurrent status is determined in substantially real-time such that any“live” updates to the application data that may be made by an applicantof the financial institution or an agent assisting the applicant arereflected in the current status in substantially real-time.

Step 3108 includes displaying, via the management platform on thedisplay system, an application timeline comprising a plurality of phasesin the application process, wherein the application timeline indicates acurrent phase of the plurality of phases in the application processbased on the current status. In one or more embodiments, the applicationtimeline may be displayed within tracking information of an applicationsection of the backend user interface (e.g., process tracker 300 ofapplication section 304 of backend user interface 200 in FIG. 2 ). Theplurality of phases of the application process may include, for example,a workflow phase, a qualify phase, a decision phase, and a processingphase. The current phase may be the phase of the application processthat is currently in progress. In one or more embodiments, theapplication process is a sequential process such that only one phase ofthe application process may be “in progress” at a time.

The application timeline may be displayed with a plurality of graphicalindicators for the plurality of phases in the application process. Thecurrent phase may be distinguished from non-current phases of theplurality of phases using, for example, an in-progress indicator. Thein-progress indicator may be a graphical indicator that distinguishesthe current phase using a certain color, text, highlighting, a certainpattern, a symbol, a graphical icon, an animation, or some other type ofvisual indication.

In one or more embodiments, the plurality of graphical indicatorsincludes a completed indicator for any phase of the plurality of phasesthat has been completed. The completed indicator may be a graphicalindicator that distinguishes the completed phase from not completedphases using a certain color, text, highlighting, a certain pattern, asymbol, a graphical icon, an animation, or some other type of visualindication.

In one or more embodiments, the plurality of graphical indicatorsincludes a remaining indicator for any phase of the plurality of phasesthat has yet to be initiated or, in other words, remains to be entered.The remaining indicator may be a graphical indicator that distinguishesthe phase that has yet to be initiated or entered from a completed orin-progress phase using a certain color, text, highlighting, a certainpattern, a symbol, a graphical icon, an animation, or some other type ofvisual indication.

Step 3110 includes displaying, via the management platform on thedisplay system, a subphase progression comprising a plurality ofsubphases within the current phase, wherein the subphase progressionindicates a current subphase of the plurality of subphases based on thecurrent status. A phase in the application process may include one ormore subphases. In one or more embodiments, the workflow phase, thequalify phase, and the processing phase include multiple subphases,while the decision phase includes a single subphase. The currentsubphase may be the subphase of the current phase that is currently inprogress. In one or more embodiments, the subphases of a phase form asequential process such that only one subphase of the phase may be “inprogress” at a time.

In one or more embodiments, the workflow phase may include at leastthree subphases selected from a group consisting of an agreementssubphase, an account subphase, a products subphase, an applicant'ssubphase, a review subphase, a funding subphase, an authenticationsubphase, and a confirmation subphase. In one or more embodiments, thequalify phase includes an identity verification subphase, an OFACsubphase, a qualifile subphase, and/or a credit reports subphase. In oneor more embodiments, the processing phase includes a funding subphase, apost to core subphase, and/or a documents subphase.

The subphase progression may be displayed with a plurality of graphicalindicators for the plurality of subphases. The current subphase may bedistinguished from non-current subphases of the plurality of phasesusing, for example, an in-progress indicator. In one or moreembodiments, a completed indicator may be used to distinguish a subphasethat has been completed. In one or more embodiments, a remainingindicator may be used to distinguish a subphase that has yet to beinitiated or, in other words, remains to be entered. The in-progressindicator, completed indicator, and remaining indicator used for thesubphases may be the same types of indicators as those used for thephases or may be different. As discussed above, the in-progressindicator, the completed indicator, and the remaining indicator may eachprovide distinction between the subphases using a certain color, text,highlighting, a certain pattern, a symbol, a graphical icon, ananimation, or some other type of visual indication.

In one or more embodiments, process 3100 optionally includes step 3112.Step 3112 may include displaying, via the management platform on thedisplay system, a current status section based on the current status.The current status section (e.g., current status section 302 in FIGS. 3and 6-9 ) may include information about at least one of the currentphase or the current subphase within the current phase. The currentstatus section may identify a most recent action of the applicant of thefrontend user interface who is progressing through the applicationprocess for the selected application and whether the applicant hascompleted the selected application. The current status section mayinclude one or more controls that allow the user of the backend userinterface to perform various actions based on the current status.

Further, in some embodiments, process 3100 may further include changingan in-progress indicator displayed via the management platform on thedisplay system for the current phase to a completed indicator insubstantially real-time in response to an action that completes thecurrent phase in the application process. The action may be performedby, for example, the applicant (e.g., user of the frontend userinterface). The applicant may be the customer, potential customer, or anagent of the financial institution.

In this manner, process 3100 improves the ability of the managementplatform to provide an accurate snapshot of the current status of anyselected application in substantially real-time. Providing theapplication timeline and subphase progression for the current phase ofthe application timeline (or for any selected phase of the applicationtimeline), along with the current status section in various embodiments,allows the management platform to provide different pieces ofinformation in a simple and visually concise way without requiringmultiple windows or pop-up window and without requiring the user toextensively navigate through the management platform to discern all ofthe information about the current status for the selected application.

FIG. 32 is a flowchart of a process for monitoring an application of auser for a set of financial products provided by a credit union inaccordance with one or more embodiments. Process 3200 may be implementedusing, for example, application system 100 in FIG. 1 . In one or moreembodiments, process 3200 may be implemented using management platform110 of application system 100 in FIG. 1 . The credit union may be, forexample, credit union 104 in FIG. 1 .

Step 3202 includes receiving, via a management platform displayed on adisplay system, an input selecting the application, wherein theapplication is associated with application data stored in an applicationdatabase. The management platform, which may be, for example, managementplatform 110 in FIG. 1 , may receive the input via a backend userinterface (e.g., backend user interface 114 in FIG. 1 ), which may bealso referred to as a management interface. The application database maybe, for example, database 111 in FIG. 1 and may be either remote orlocal to the display system.

In one or more embodiments, the input may be received via the backenduser interface on a display system that is owned, operated by, and/orotherwise in use by a credit union such as credit union 104 in FIG. 1 .This display system (e.g., the screen of a mobile device, laptop,desktop, tablet, etc.) may be located remotely with respect to, forexample, application system 100, which may be owned, operated by, and/orotherwise in use by an entity such as entity 103 in FIG. 1 . Themanagement platform is in communication with the application databaseand capable of retrieving the application data from the applicationdatabase.

Step 3204 includes determining a current status of an applicationprocess corresponding to the application using the application dataassociated with the selected application. The current status may bedetermined based on, for example, whether the application is inprogress, whether the application has completed a qualification process,whether a decision has been regarding the application (e.g.,approval/denial), whether the application has been processedpost-decision, and/or other information. In one or more embodiments, thecurrent status is determined in substantially real-time such that any“live” updates to the application data that may be made by an applicantof the credit union or an agent assisting the applicant are reflected inthe current status in substantially real-time.

Step 3206 includes displaying, via the management platform, anapplication timeline comprising a plurality of phases in the applicationprocess. The plurality of phases includes a workflow phase and at leastone of a qualify phase, a decision phase, or a processing phase. Theapplication timeline may indicate, based on the current status, that theworkflow phase is a current phase in the application process using afirst in-progress indicator.

Step 3208 includes displaying, via the management platform on thedisplay system, a subphase progression comprising a plurality ofsubphases within the workflow phase. This subphase progression may bereferred to as, for example, a workflow subphase progression (e.g.,workflow subphase progression 614 in FIG. 6 ). The plurality ofsubphases may include at least three selected from a group consisting ofan agreements subphase, an account subphase, a products subphase, anapplicant's subphase, a review subphase, a funding subphase, anauthentication subphase, and a confirmation subphase. The subphaseprogression indicates, based on the current status, a current subphaseof the plurality of subphases using a second in-progress indicator. Thesecond in-progression indicator may be the same type of indicator as thefirst in-progress indicator (e.g., using the same color, same text, samehighlighting, same pattern, same symbol, same graphical icon, sameanimation, etc.) or may be different.

In one or more embodiments, process 3200 optionally includes step 3210.Step 3210 may include displaying, via the management platform on thedisplay system, a current status section based on the current status.The current status section may identify, for example, a most recentaction of the applicant of the frontend user interface and whether theapplicant has completed the selected application. The current stationmay include, for example, a graphical control that, when selected, opensa corresponding workflow for the application of the applicant. Forexample, selecting the graphical control may open a new window or newweb browser that displays the frontend user interface with theapplication data for the application populated.

FIG. 33 is a flowchart of a process for building an online applicationplatform for a client financial institution in accordance with one ormore embodiments. Process 3300 may be implemented using, for example,application system 100 in FIG. 1 . In one or more embodiments, process3300 may be implemented using management platform 110 of applicationsystem 100 in FIG. 1 . The online application platform may be, forexample, application platform 108 in FIG. 1. Process 3300 may be used tocustomize a default configuration of the online application platform.

Step 3302 includes providing a default configuration for the onlineapplication platform. The default configuration may include a defaultapplication framework and a default theme. The default applicationframework defines a default set of account types and a default set offinancial products for an application. The default theme defines anappearance of the online application platform. The default configurationfor the online application platform is provided to a client financialinstitution (e.g., financial institution 102 in FIG. 1 ).

Step 3304 includes providing a management interface accessible by theclient financial institution, the management interface including anapplication framework tool for customizing the default applicationframework and a theme tool for customizing the default theme. Themanagement interface may be, for example, backend user interface 114 inFIG. 1 and/or backend user interface 200 in FIGS. 2-22, 24, 26, 28, and30 . The application framework tool may be, for example, framework tool118 in FIG. 1 and/or framework tool 1707 in FIGS. 17-21 . The theme toolmay be, for example, theme tool 122 in FIG. 1 and/or theme tool 3000 inFIG. 30 .

Step 3306 includes receiving, by the application framework tool, a firstset of inputs that selects a set of financial products from a list ofpredefined financial products, wherein the set of financial products isto be offered by the client financial institution via the onlineapplication platform. The first set of inputs may be entered by, forexample, an agent (e.g., administrator) of the financial institution.The list of predefined financial products may include, for example,without limitation, at least one type of savings account, at least onetype of checking account, at least one type of CD, at least one type ofmoney market account, at least one type of club account, or acombination thereof. In one or more embodiments, the list of predefinedfinancial products includes at least three selected from a groupconsisting of a checking account, a savings account, a money marketaccount, a certificate of deposit, a loan, and a trust. The default setof financial products included in the default application framework mayinclude one, some, or all of the financial products in the list ofpredefined financial products.

In one or more embodiments, the first set of inputs includes an inputthat deselects a financial product in the default set of financialproducts. This deselection may not remove the financial product from thelist of predefined financial products but may deactivate the financialproduct (e.g., prevent the financial product from being offered via theonline application platform).

In one or more embodiments, the first set of inputs includes an inputthat selects a financial product from the list of predefined financialproducts that is not already present in the default set of financialproducts. This input may activate the financial product (e.g., makingthe financial product available via the online application platform).

In one or more embodiments, the first set of inputs includes an input orgroup of inputs that adds a new financial product to the list ofpredefined financial products, as well as corresponding details for thenew financial product. The new financial product may be activated ordeactivated.

Step 3308 includes converting, by the application framework tool, thedefault application framework into a customized application framework,the converting comprising modifying the online application platform tooffer the set of financial products selected via the first set ofinputs. This conversion changes the default set of financial products tothe set of financial products to thereby customize the offerings of thefinancial institution.

In one or more embodiments, step 3308 may further include customizingbased on one or more other sets of inputs received in step 3306 or inanother optional step(s) before step 3308. For example, in response to aset of inputs received that select a set of account types form a list ofpredefined account types (the set of account types being different fromthe default set of account types) for the application framework, theconversion may include modifying the online application platform to makethe set of account types available. In one or more embodiments, eachaccount type may correspond to a different type of membership (e.g., apersonal account/membership, a teen account/membership, a youthaccount/membership, a business account/membership, etc.) for the clientfinancial institution.

In one or more embodiments, in response to receiving a set of inputsthat add a set of document types to the application framework, theconversion may include modifying the online application platform to atleast one of generate or an enable an upload of the set of documenttypes. Adding a document type may include, for example, uploading a PDFtemplate of a document type that will serve as the basis for a financialdisclosure document to be generated during an application process. ThePDF template may be uploaded in a format (e.g., with fields names and/orcoded according to a set of rules, requirements, and/or other criteria)that allows the management platform to correctly populate fields in thegenerated financial disclosure document with application data retrievedfrom the application database.

In one or more embodiments, in response to receiving a set of inputsthat select a set of product groups from a list of predefined productgroups that is different from a default set of product groups includedin the default application framework, the conversion may includemodifying the online application platform to allow only financialproducts corresponding to the set of product groups to be offered.

In one or more embodiments, in response to receiving a set of inputsthat select a set of third-party services from a list of predefinedthird-party services that is different from a default set of third partyservices included in the default application framework, the conversionincludes modifying the online application platform to allowcommunication between the online application platform and the set ofthird-party services. One example of a third party service may be, forexample, a credit reporting agency.

Step 3310 includes receiving, by the theme tool, a second set of inputsfrom the financial institution, each input of the second set of inputsselecting a value for a respective characteristic of the appearance ofthe online application platform, the value corresponding with a brandingof the client financial institution. A characteristic may be, forexample, a color, a font, a logo, or some other appearance-basedcharacteristic. The theme tool may include, for example, acharacteristic modifier for making changes to a plurality ofcharacteristics and a preview section that previews the appearance ofthe online application platform (e.g., frontend user interface 112 ofapplication platform 108) based on the changes.

In one or more embodiments, the second set of inputs includes at leastone of an input selecting a value for a primary color of the appearanceof the online application platform, an input selecting a value for asecondary color of the appearance of the online application platform, aninput selecting a value for an accent color of the appearance of theonline application platform, or an input selecting a value for analternate color of the appearance of the online application platform. Inone or more embodiments, the second set of inputs includes at least oneof an input selecting a value for a background color of the appearanceof the online application platform, an input selecting a value for abody text color of the appearance of the online application platform, aninput selecting a value for a success color for the online applicationplatform, or an input selecting a value for an error color for theonline application platform.

In one or more embodiments, the second set of inputs includes an inputthat selects a value for the characteristic of a logo for the onlineapplication platform, where the value comprises an image for the logo.For example, an image file may be uploaded for the logo.

Step 3312 includes converting, by the theme tool, the default theme intoa customized theme, the converting comprising modifying the appearanceof the online application platform to reflect the value for thecharacteristic. In one or more embodiments, the customized theme mayrepresent a branding of the client financial institution more closelythan the default theme.

Step 3314 includes providing, via a network, a customized configurationof the online application platform to one or more applicants of theclient financial institution, the customized configuration comprisingthe customized application framework and the customized theme. Thenetwork may include, for example, the Internet.

In this manner, process 3300 enables a fast, easy, and efficient way ofbuilding and deploying a customized online application platform. Process3300 provides a customizable configuration of an online applicationplatform to a financial institution, where the customizableconfiguration already includes workflows and features relevant to thefinancial institution—thus eliminating the need for the financialinstitution to build an online application platform from scratch. Forexample, using the framework tool and the theme tool may help reduce thecomputing resources used in the customization of the online applicationplatform. Further, by providing a management interface (backend userinterface) that includes both the framework tool and the theme tool,on-demand changes may be made to the online application platform. Inother embodiments, a similar process may be used to convert a currentconfiguration of the online application platform into a newconfiguration of the online application platform.

In one or more embodiments, the application system 100 and process 3300improves the technical field of online application systems by improvingthe customization and processing of applications for membership andapplications for financial products.

FIG. 34 is a flowchart of a process for customizing an applicationplatform for a client financial institution in accordance with one ormore embodiments. Process 3400 may be implemented using, for example,application system 100 in FIG. 1 . In one or more embodiments, process3400 may be implemented using management platform 110 of applicationsystem 100 in FIG. 1 .

Step 3402 includes providing a default configuration for the onlineapplication platform, the default configuration comprising a defaultapplication framework and a default theme. The default applicationframework defines a default set of account types and a default set offinancial products for an application.

Step 3404 includes providing a management interface accessible by theclient financial institution, the management interface including aframework tool for customizing the default application framework.

Step 3406 includes receiving, by the framework tool, a first set ofinputs that selects a set of account types from a list of predefinedaccount types, wherein each of the set of account types corresponds to adifferent type of membership for the client financial institution.

Step 3408 includes receiving, by the framework tool, a second set ofinputs that selects a set of financial products from a list ofpredefined financial products, wherein the set of financial products isto be offered by the client financial institution via the onlineapplication platform. In one or more embodiments, the list of predefinedfinancial products may be based on the set of product groups.

Step 3410 includes receiving, by the framework tool, a third set ofinputs that selects a set of third-party services from a list ofpredefined third-party services.

Step 3412 includes converting, by the framework tool, the defaultapplication framework into a customized application framework, theconverting comprising modifying the online application platform based onthe first set of inputs, the second set of inputs, and the third set ofinputs.

The flowcharts and block diagrams in the different depicted embodimentsillustrate the architecture, functionality, and operation of somepossible implementations of apparatuses and methods in an illustrativeembodiment. In this regard, each block in the flowcharts or blockdiagrams may represent a module, a segment, a function, and/or a portionof an operation or step.

In some alternative implementations of an illustrative embodiment, thefunction or functions noted in the blocks may occur out of the ordernoted in the figures. For example, in some cases, two blocks shown insuccession may be executed substantially concurrently, or the blocks maysometimes be performed in the reverse order, depending upon thefunctionality involved. Also, other blocks may be added in addition tothe illustrated blocks in a flowchart or block diagram.

Turning now to FIG. 35 , an illustration of a data processing system inthe form of a block diagram is depicted in accordance with one or moreembodiments. Data processing system 3500 may be used to implement atleast a portion of computing system 106 in FIG. 1 . As depicted, dataprocessing system 3500 includes communications framework 3502, whichprovides communications between processor unit 3504, storage devices3506, communications unit 3508, input/output unit 3510, and display3512. In some cases, communications framework 3502 may be implemented asa bus system.

Processor unit 3504 is configured to execute instructions for softwareto perform a number of operations. Processor unit 3504 may comprise anumber of processors, a multi-processor core, and/or some other type ofprocessor, depending on the implementation. In some cases, processorunit 3504 may take the form of a hardware unit, such as a circuitsystem, an application specific integrated circuit (ASIC), aprogrammable logic device, or some other suitable type of hardware unit.

Instructions for the operating system, applications, and/or programs runby processor unit 3504 may be located in storage devices 3506. Storagedevices 3506 may be in communication with processor unit 3504 throughcommunications framework 3502. As used herein, a storage device, alsoreferred to as a computer readable storage device, is any piece ofhardware capable of storing information on a temporary and/or permanentbasis. This information may include, but is not limited to, data,program code, and/or other information.

Memory 3514 and persistent storage 3516 are examples of storage devices3506. Memory 3514 may take the form of, for example, a random accessmemory or some type of volatile or non-volatile storage device.Persistent storage 3516 may comprise any number of components ordevices. For example, persistent storage 3516 may comprise a hard drive,a flash memory, a rewritable optical disk, a rewritable magnetic tape,or some combination of the above. The media used by persistent storage3516 may or may not be removable.

Communications unit 3508 allows data processing system 3500 tocommunicate with other data processing systems and/or devices.Communications unit 3508 may provide communications using physicaland/or wireless communications links.

Input/output unit 3510 allows input to be received from and output to besent to other devices connected to data processing system 3500. Forexample, input/output unit 3510 may allow user input to be receivedthrough a keyboard, a mouse, and/or some other type of input device. Asanother example, input/output unit 3510 may allow output to be sent to aprinter connected to data processing system 3500.

Display 3512 is configured to display information to a user. Display3512 may comprise, for example, without limitation, a monitor, a touchscreen, a laser display, a holographic display, a virtual displaydevice, and/or some other type of display device.

In this illustrative example, the processes of the differentillustrative embodiments may be performed by processor unit 3504 usingcomputer-implemented instructions. These instructions may be referred toas program code, computer usable program code, or computer readableprogram code and may be read and executed by one or more processors inprocessor unit 3504.

In these examples, program code 3518 is located in a functional form oncomputer readable media 3520, which is selectively removable, and may beloaded onto or transferred to data processing system 3500 for executionby processor unit 3504. Program code 3518 and computer readable media3520 together form computer program product 3522. In this illustrativeexample, computer readable media 3520 may be computer readable storagemedia 3524 or computer readable signal media 3526.

Computer readable storage media 3524 is a physical or tangible storagedevice used to store program code 3518 rather than a medium thatpropagates or transmits program code 3518. Computer readable storagemedia 3524 may be, for example, without limitation, an optical ormagnetic disk or a persistent storage device that is connected to dataprocessing system 3500.

Alternatively, program code 3518 may be transferred to data processingsystem 3500 using computer readable signal media 3526. Computer readablesignal media 3526 may be, for example, a propagated data signalcontaining program code 3518. This data signal may be an electromagneticsignal, an optical signal, and/or some other type of signal that can betransmitted over physical and/or wireless communications links.

The illustration of data processing system 3500 in FIG. 35 is not meantto provide architectural limitations to the manner in which theillustrative embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system that includescomponents in addition to or in place of those illustrated for dataprocessing system 3500. Further, components shown in FIG. 35 may bevaried from the illustrative examples shown.

As used herein, the phrase “at least one of,” when used with a list ofitems, means different combinations of one or more of the listed itemsmay be used and only one of the items in the list may be needed. Theitem may be a particular object, thing, step, operation, process, orcategory. In other words, “at least one of” means any combination ofitems or number of items may be used from the list, but not all of theitems in the list may be required. For example, without limitation, “atleast one of item A, item B, or item C” or “at least one of item A, itemB, and item C” may mean item A; item A and item B; item B; item A, itemB, and item C; item B and item C; or item A and C. In some cases, “atleast one of item A, item B, or item C” or “at least one of item A, itemB, and item C” may mean, but is not limited to, two of item A, one ofitem B, and ten of item C; four of item B and seven of item C; or someother suitable combination.

The description of the different embodiments has been presented forpurposes of illustration and description and is not intended to beexhaustive or limited to the embodiments in the form disclosed.Modifications and variations will be apparent to those of ordinary skillin the art. Further, different embodiments may include differentfeatures as compared to other embodiments. The one or more embodimentsdescribed are chosen and described in order to best explain theprinciples of the various embodiments and practical application of theseembodiments, and to enable others of ordinary skill in the art tounderstand the various modifications to the various embodiments that maybe suited to the particular use(s) contemplated.

What is claimed is:
 1. A method for monitoring a plurality ofapplications for a set of financial products provided by a financialinstitution, the method comprising: displaying the plurality ofapplications via a management platform on a display system, wherein eachapplication of the plurality of applications is associated withapplication data stored in an application database; receiving user inputidentifying a selected application from the plurality of applications;determining a current status of an application process corresponding tothe selected application using the application data associated with theselected application; displaying, via the management platform on thedisplay system, an application timeline comprising a plurality of phasesin the application process, wherein the application timeline indicates acurrent phase of the plurality of phases in the application processbased on the current status; and displaying, via the management platformon the display system, a subphase progression comprising a plurality ofsubphases within the current phase, wherein the subphase progressionindicates a current subphase of the plurality of subphases based on thecurrent status.
 2. The method of claim 1, wherein displaying, via themanagement platform on the display system, the application timelinecomprises: displaying, via the management platform on the displaysystem, the application timeline with a plurality of graphicalindicators for the plurality of phases in the application process,wherein the plurality of graphical indicators includes an in-progressindicator for the current phase of the plurality of phases thatindicates that the current phase is in-progress.
 3. The method of claim1, wherein displaying, via the management platform on the displaysystem, the application timeline comprises: displaying, via themanagement platform on the display system, the application timeline witha plurality of graphical indicators for the plurality of phases in theapplication process, wherein the plurality of graphical indicatorsincludes a completed indicator for a corresponding phase of theplurality of phases that indicates that the corresponding phase has beencompleted.
 4. The method of claim 1, further comprising: changing anin-progress indicator displayed via the management platform on thedisplay system for the current phase to a completed indicator insubstantially real-time in response to an action that completes thecurrent phase in the application process.
 5. The method of claim 1,wherein the current phase is a workflow phase and wherein displaying,via the management platform on the display system, the subphaseprogression comprises: displaying, via the management platform on thedisplay system, a workflow progression corresponding to the workflowphase, wherein the plurality of subphases within the workflow phaseincludes at least three selected from a group consisting of anagreements subphase, an account subphase, a products subphase, anapplicants subphase, a review subphase, a funding subphase, anauthentication subphase, and a confirmation subphase.
 6. The method ofclaim 5, wherein displaying, via the management platform on the displaysystem, the workflow progression comprises: displaying, via themanagement platform on the display system, the workflow progression witha plurality of graphical indicators for the plurality of subphases inthe workflow phase, wherein the current subphase of the workflow phaseis distinguished from non-current subphases of the workflow phase by anin-progress indicator.
 7. The method of claim 5, wherein displaying, viathe management platform on the display system, the workflow progressioncomprises: displaying, via the management platform on the displaysystem, the workflow progression with a plurality of graphicalindicators for the plurality of subphases in the workflow phase, whereinthe plurality of graphical indicators includes a completed indicator fora first subphase of the plurality of subphases that indicates that thefirst subphase is completed; and wherein the plurality of graphicalindicators includes a remaining indicator for a second subphase of theplurality of subphases that indicates that the second subphase remainsto be entered.
 8. The method of claim 1, further comprising: displaying,via the management platform on the display system, a current statussection that includes information about at least one of the currentphase or the current subphase within the current phase.
 9. The method ofclaim 1, further comprising: displaying, via the management platform onthe display system, a current status section that identifies a mostrecent action of an applicant who is progressing through the applicationprocess for the selected application and whether the applicant hascompleted the selected application.
 10. The method of claim 1, furthercomprising: receiving a new user input that selects, via the applicationtimeline, a non-current phase of the plurality of phases; removing, fromthe management platform on the display system, the subphase progressionfor the plurality of subphases within the current phase; and displaying,via the management platform on the display system, a new subphaseprogression for a set of subphases within the non-current phase.
 11. Asystem for monitoring a plurality of applications for a set of financialproducts provided by a financial institution, the system comprising: amemory containing a machine-readable medium containing instructions; anda processor coupled to the memory, the processor configured to executethe instructions to cause the processor to: display the plurality ofapplications via a management platform on a display system, wherein eachapplication of the plurality of applications is associated withapplication data stored in an application database; receive user inputidentifying a selected application from the plurality of applications;determine a current status of an application process corresponding tothe selected application using the application data associated with theselected application; display, via the management platform, anapplication timeline comprising a plurality of phases in the applicationprocess, wherein the application timeline indicates a current phase ofthe plurality of phases in the application process based on the currentstatus; and display, via the management platform, a subphase progressioncomprising a plurality of subphases within the current phase, whereinthe subphase progression indicates a current subphase of the pluralityof subphases based on the current status.
 12. The system of claim 11,wherein the processor is further configured to execute the instructionsto cause the processor to change an in-progress indicator displayed viathe management platform for the current phase to a completed indicatorin substantially real-time in response to an action that completes thecurrent phase in the application process.
 13. The system of claim 11,wherein the current phase is a workflow phase and wherein the pluralityof subphases within the workflow phase includes at least three selectedfrom a group consisting of an agreements subphase, an account subphase,a products subphase, an applicants subphase, a review subphase, afunding subphase, an authentication subphase, and a confirmationsubphase.
 14. The system of claim 11, wherein: the application timelineindicates the current phase using a first in-progress indicator thatdistinguishes the current phase from a non-current phase of theplurality of phases; and the subphase progression indicates the currentsubphase using a second in-progress indicator that distinguishes thecurrent subphase from a non-current subphase of the plurality ofsubphases.
 15. The system of claim 11, wherein the subphase progressionincludes an in-progress indicator that identifies the current subphase,a completed indicator that identifies a completed subphase of theplurality of subphases, and a remaining indicator that identifies asubphase that remains to be entered.
 16. The system of claim 11, whereinthe processor is further configured to execute the instructions to causethe processor to display, via the management platform, a current statussection that includes information about at least one of the currentphase or the current subphase within the current phase.
 17. The systemof claim 11, wherein the processor is further configured to execute theinstructions to cause the processor to display, via the managementplatform, a current status section that identifies a most recent actionof an applicant who is progressing through the application process forthe selected application and whether the applicant has completed theselected application.
 18. The system of claim 11, wherein the processoris further configured to execute the instructions to cause the processorto: receive a new user input that selects, via the application timeline,a non-current phase of the plurality of phases; remove, from themanagement platform on the display system, the subphase progression forthe plurality of phases within the current phase; and display, via themanagement platform on the display system, a new subphase progressionfor a set of phases within the non-current phase.
 19. A method formonitoring an application of an applicant for a plurality of financialproducts provided by a credit union, the method comprising: receiving,via a management platform displayed on a display system, an inputselecting the application, wherein the application is associated withapplication data stored in an application database; determining acurrent status of an application process corresponding to theapplication using the application data associated with the selectedapplication; displaying, via the management platform, an applicationtimeline comprising a plurality of phases in the application process,wherein the plurality of phases includes a workflow phase and at leastone of a qualify phase, a decision phase, or a processing phase; whereinthe application timeline indicates, based on the current status, thatthe workflow phase is a current phase in the application process using afirst in-progress indicator; and displaying, via the management platformon the display system, a subphase progression comprising a plurality ofsubphases within the workflow phase, wherein the subphase progressionindicates, based on the current status, a current subphase of theplurality of subphases using a second in-progress indicator.
 20. Themethod of claim 19, further comprising: displaying, via the managementplatform on the display system, a current status section that identifiesa most recent action of the applicant and whether the applicant hascompleted the selected application, wherein the current status sectionincludes a graphical control that, when selected, opens a correspondingworkflow for the application of the applicant.